feat(grpc): add configurable maximum size limit for received gRPC messages#3048
Conversation
…sages Signed-off-by: Jordan McClintock <jordan@defenseunicorns.com>
corang
force-pushed
the
feat/grpc-configurable-size-limit
branch
from
e6c1b4a to
561ae62
Compare
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
migmartri
left a comment
migmartri
left a comment
There was a problem hiding this comment.
LGTM, please fix the conflict and let me know.
BTW, while testing your PR we noticed some mayor improvements in the attestation #3056 push payload that will reduce the size of that payload ~60%. What API calls were causing you the error?
Signed-off-by: Jordan McClintock <jordan@defenseunicorns.com>
It was just using the |
|
@philiposs could you please backport this fix to chainloop-ee chart? thanks! |
2 participants
Adds a configurable
max_recv_msg_sizeoption to the controlplane gRPC server, allowing operators to increase the default 4MB message size limit. This resolvesResourceExhaustederrors when pushing attestations larger than 4MB (e.g., attestations with large SBOMs or SARIF reports).The setting is exposed end-to-end:
Server.GRPCcontrolplane.grpcMaxRecvMsgSizeWhen unset, the standard gRPC default of 4MB applies.
Example Helm usage: